Attempts to fix the issue where scheduled weekly releases don't trigger CI builds.

Problem

Release events created by workflows using GITHUB_TOKEN don't trigger other workflows (GitHub Actions security policy to prevent recursive workflow triggering).

Solution

1. Remove explicit token references - Let GitHub Actions handle authentication automatically instead of explicitly setting GH_TOKEN or GITHUB_TOKEN in env
2. Add --notes-start-tag - Generate sparse release notes comparing only against previous weekly tag (prevents pinging everyone with full history)
3. Add --fail-on-no-commits - Prevent empty releases when no work has been done since last release

Changes

• Modified .github/workflows/scheduled-releases.yml
• Removed env: GH_TOKEN: ${{ secrets.GITHUB_TOKEN }} block
• Added logic to find previous weekly tag
• Added --notes-start-tag "$PREV_TAG" to gh release create command
• Added --fail-on-no-commits flag

Testing

Can be tested via:

• Manual trigger: workflow_dispatch on Actions tab
• Automated: Wait for next Wednesday's scheduled run (Oct 23)

Related

• Issue: Scheduled releases not triggering CI builds (discovered Oct 9 sync)
• PR Use release events to trigger builds from automated weekly releases #744 - Original release trigger fix attempt (switched from tag to release events, but didn't trigger release build)

See also

• https://cli.github.com/manual/gh_release_create
• https://docs.github.com/en/webhooks/webhook-events-and-payloads?actionType=published#release
• https://docs.github.com/en/actions/how-tos/write-workflows/choose-when-workflows-run/trigger-a-workflow#triggering-a-workflow-from-a-workflow
• https://docs.github.com/en/actions/tutorials/authenticate-with-github_token